@V-Paranoiaque will have a look at it tomorrow. Again I don't have a ready setup to test this, but I can offer suggestions based off of the docker setup and any blaring issues that might come up.
Testing is upto the community for this PR as I don't have the time to setup and cluster and test this now.

I have done some fixes and deployed it on my cluster, no issue for the moment

Thanks for putting this chart together!
I dont have time to weekend to check it myself but I thought I would use @codex and give a quick check

These might be useful to double check @V-Paranoiaque :

• The deployment image is always rendered with a leading 'v' (e.g. ghcr.io/raylabshq/gitea-mirror:v3.7.2), but the published tags are unprefixed; that breaks image resolution for defaults and custom tags.
• Inside the deployment template, the annotation/resources with-blocks still reference .Values..., so enabling those blocks causes the render to fail with 'can't evaluate field Values'.
• MIRROR_STARRED is wired to gitea-mirror.mirror.starred, but values/docs expose gitea-mirror.github.mirrorStarred; as written the user-provided flag is ignored.
• The cleanup retention env var is emitted as CLEANUP_INTERVAL while the app expects CLEANUP_RETENTION_DAYS (and values expose cleanup.retentionDays), so retention can't be configured.
• ingress.hosts[].paths[].path and ingress.pathType values are ignored because the template hardcodes '/' and 'Prefix'.

Hope this helps!

I have fixed the problems, except for the image's tag. The images are prefixed with "v" so it should work.
I don't use an ingress so it might still need some fixing. Would be great to have a new check with @codex